Grokking System Design Fundamentals
Rate this course
Ask Author
Contribute
Back to course home

94% completed

Vote For New Content
System Design Fundamentals
Introduction to System Design
Load Balancing
Introduction to Load Balancing
Load Balancing Algorithms
Uses of Load Balancing
Load Balancer Types
Stateless vs. Stateful Load Balancing
High Availability and Fault Tolerance
Scalability and Performance
Challenges of Load Balancers
API Gateway
Introduction to API Gateway
Usage of API gateway
Advantages and disadvantages of using API gateway
Key Characteristics of Distributed Systems
Scalability
Availability
Latency and Performance
Concurrency and Coordination
Monitoring and Observability
Resilience and Error Handling
Fault Tolerance vs. High Availability
Network Essentials
HTTP vs. HTTPS
TCP vs. UDP
HTTP: 1.0 vs. 1.1 vs 2.0 vs. 3.0
URL vs. URI vs. URN
Domain Name System (DNS)
Introduction to DNS
DNS Resolution Process
DNS Load Balancing and High Availability
Caching
Introduction to Caching
Why is Caching Important?
Types of Caching
Cache Replacement Policies
Cache Invalidation
Cache Read Strategies
Cache Coherence and Consistency Models
Caching Challenges
Cache Performance Metrics
CDN
What is CDN?
Origin Server vs. Edge Server
CDN Architecture
Push CDN vs. Pull CDN
Data Partitioning
Introduction to Data Partitioning
Partitioning Methods
Data Sharding Techniques
Benefits of Data Partitioning
Common Problems Associated with Data Partitioning
Proxies
What is a Proxy Server?
Uses of Proxies
VPN vs. Proxy Server
Redundancy and Replication
What is Redundancy?
What is Replication?
Replication Methods
Data Backup vs. Disaster Recovery
CAP & PACELC Theorems
Introduction to CAP Theorem
Components of CAP Theorem
Trade-offs in CAP Theorem
Examples of CAP Theorem in Practice
Beyond CAP Theorem
System Design Trade-offs in Interviews
Databases (SQL vs. NoSQL)
Introduction to Databases
SQL Databases
NoSQL Databases
SQL vs. NoSQL
ACID vs BASE Properties
Real-World Examples and Case Studies
SQL Normalization and Denormalization
In-Memory Database vs. On-Disk Database
Data Replication vs. Data Mirroring
Database Federation
Indexes
What are Indexes?
Types of Indexes
Bloom Filters
Introduction to Bloom Filters
Benefits & Limitations of Bloom Filters
Variants and Extensions of Bloom Filters
Applications of Bloom Filters
Long-Polling vs. WebSockets vs. Server-Sent Events
Difference Between Long-Polling, WebSockets, and Server-Sent Events
Quorum
What is Quorum?
Heartbeat
What is Heartbeat?
Checksum
What is Checksum?
Uses of Checksum
Leader and Follower
What is Leader and Follower Pattern?
Security
What is Security and Privacy?
What is Authentication?
What is Authorization?
Authentication vs. Authorization
OAuth vs. JWT for Authentication
What is Encryption?
What are DDoS Attacks?
Distributed Messaging System
Introduction to Messaging System
Introduction to Kafka
Messaging patterns
Popular Messaging Queue Systems
RabbitMQ vs. Kafka vs. ActiveMQ
Scalability and Performance
Distributed File Systems
What is a Distributed File System?
Architecture of a Distributed File System
Key Components of a DFS
Misc Concepts
Batch Processing vs. Stream Processing
XML vs. JSON
Synchronous vs. Asynchronous Communication
Push vs. Pull Notification Systems
Microservices vs. Serverless Architecture
Message Queues vs. Service Bus
Stateful vs. Stateless Architecture
Event-Driven vs. Polling Architecture
Quiz
Push vs. Pull Notification Systems

Push and pull notification systems are two distinct methods used in software and web applications for updating users with new information. Understanding the differences between them is crucial for designing effective and user-friendly notification mechanisms.

Push Notification System

Definition

  • Push Notifications involve sending information to users proactively from a server. The server initiates the data transmission.

Characteristics

  • Proactive: The server sends notifications without the user requesting them.
  • Real-Time: Offers near-instant delivery of messages, making it suitable for timely alerts.
  • User Engagement: Can enhance user engagement but requires careful management to avoid overwhelming users.

Use Cases

  • New email or instant message alerts.
  • Social media updates (like new posts or interactions).
  • App-specific alerts, like a ride-sharing app notifying users of ride status.

Example

  • A weather app sends a push notification about a sudden weather change.

Pros and Cons

  • Pros: Immediate information delivery; no action required from users to receive updates.
  • Cons: Can be intrusive; relies on users granting permission to receive notifications.

Pull Notification System

Definition

  • Pull Notifications require the user or client to actively request or check for new information.

Characteristics

  • Reactive: The user must initiate the process to check for new updates.
  • Manual Refresh: Users may need to refresh or query the server for the latest updates.
  • Control: Users have more control over when they receive information.

Use Cases

  • Checking for new emails by refreshing the email client.
  • Manually updating a news app to see the latest articles.
  • Polling a server for the latest updates in a collaborative application.

Example

  • A user opens a social media app to check for new messages or notifications.

Pros and Cons

  • Pros: Less intrusive; users access information at their convenience.
  • Cons: Not suitable for urgent updates; relies on user action to receive new information.

Key Differences

  1. Initiation:

    • Push: Server-initiated.
    • Pull: Client/user-initiated.
  2. Timeliness:

    • Push: Notifications are instant and automatic.
    • Pull: Updates are obtained on demand, possibly leading to delays.
  3. User Engagement:

    • Push: Can increase engagement through timely and relevant notifications.
    • Pull: Requires active user engagement to seek out information.
  4. Intrusiveness:

    • Push: Potentially more intrusive, can lead to notification fatigue.
    • Pull: Less intrusive, as users control when they receive updates.
  5. Internet Dependency:

    • Push: Requires a constant internet connection for real-time updates.
    • Pull: Users can check for updates whenever they have internet access.
  6. Implementation Complexity:

    • Push: Generally more complex to implement; requires maintaining connections and managing permissions.
    • Pull: Simpler to implement; typically involves standard request-response models.

Conclusion

The choice between push and pull notification systems depends on the application's nature, the type of information being disseminated, and user preferences. Push notifications are ideal for critical and time-sensitive updates, while pull notifications are better suited for non-urgent information that users can access at their leisure.

Synchronous vs. Asynchronous Communication
Microservices vs. Serverless Architecture
Mark as Completed

On this page

Push Notification System

Definition

Characteristics

Use Cases

Example

Pros and Cons

Pull Notification System

Definition

Characteristics

Use Cases

Example

Pros and Cons

Key Differences

Conclusion